-
-
Couldn't load subscription status.
- Fork 3.7k
cleanups, especially to loggers #10865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks for your pull request! This pull request does not follow the contribution rules. Could you have a look? ❌ All commit messages should start with a JIRA issue key matching pattern › This message was automatically generated. |
| if ( LOG.isTraceEnabled() ) { | ||
| LOG.trace( "Persisting " + infoString( persister, id, source.getFactory() ) ); | ||
| if ( log.isTraceEnabled() ) { | ||
| log.trace( "Persisting " + infoString( persister, id, source.getFactory() ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| if ( LOG.isTraceEnabled() ) { | ||
| LOG.trace( "Deleting " + infoString( persister, entityEntry.getId(), session.getFactory() ) ); | ||
| if ( log.isTraceEnabled() ) { | ||
| log.trace( "Deleting " + infoString( persister, entityEntry.getId(), session.getFactory() ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| if ( status == Status.DELETED ) { | ||
| if ( !persister.isMutable() ) { | ||
| LOG.trace( "Updating immutable, deleted entity: " + info ); | ||
| log.trace( "Updating immutable, deleted entity: " + info ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| } | ||
| else if ( !entry.isModifiableEntity() ) { | ||
| LOG.trace( "Updating non-modifiable, deleted entity: " + info ); | ||
| log.trace( "Updating non-modifiable, deleted entity: " + info ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| } | ||
| else { | ||
| LOG.trace( "Updating deleted entity: " + info ); | ||
| log.trace( "Updating deleted entity: " + info ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| if ( log.isTraceEnabled() ) { | ||
| if ( Hibernate.isInitialized( obj ) ) { | ||
| LOG.tracev( "Starting serialization of object [{0}]", obj ); | ||
| log.tracev( "Starting serialization of object [{0}]", obj ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| if ( LOG.isTraceEnabled() ) { | ||
| LOG.tracev( "Getting version: {0}", infoString( this, id, getFactory() ) ); | ||
| if ( log.isTraceEnabled() ) { | ||
| log.tracev( "Getting version: {0}", infoString( this, id, getFactory() ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| if ( LOG.isTraceEnabled() ) { | ||
| LOG.tracev( "Fetching entity: {0}", infoString( this, id, getFactory() ) ); | ||
| if ( log.isTraceEnabled() ) { | ||
| log.tracev( "Fetching entity: {0}", infoString( this, id, getFactory() ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| log.trace( "Collection fully initialized: " | ||
| + collectionInfoString( collectionDescriptor, collection, key, session ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| log.trace( "Caching collection: " | ||
| + collectionInfoString( collectionDescriptor, collection, key, session ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
and stricter enforcement of @DiscriminatorValue requirement (I don't think this is a substantive change to behavior, but it might be).
|
I personally would prefer to stick to UPPER_CASE for static final variables like |
| log.trace( "Collection dereferenced: " | ||
| + collectionInfoString( loadedPersister, collection, entry.getLoadedKey(), session ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| log.trace( "Found collection with unloaded owner: " | ||
| + collectionInfoString( loadedPersister, collection, loadedKey, session ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
| log.trace( "Skipping uninitialized bytecode-lazy collection: " | ||
| + collectionInfoString( persister, collection, collectionEntry.getCurrentKey(), session ) ); |
Check failure
Code scanning / CodeQL
Insertion of sensitive information into log files High
potentially sensitive information
I really don't think it matters much at all if these are lower or upper case. I very slightly prefer lowercase because it makes the log statements stand out somewhat less. (Logging crap is ugly enough without having it shouting at me.) But I do think it's a good idea to be at least consistent across the whole code base. And we're not consistent right now. Whatever, I'm not going to redo this work. But I'm not going try to to stop you renaming everything to uppercase, as long as you do it everywhere. |
|
replaced by #10879 |
[Please describe here what your change is about]
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.